| 343 |
 | 5.11 |
| |
| 1 |
|  |
| 449 |
| 5.10 |
| |
| 27 |
| |
| 460 |
 | 5.0.9 |
| |
| 7 |
|
| |
| 3 |
|
| Agents |
| |
| 3 |
|
| |
| 1 |
|
| Applet Component |
| |
| 1 |
|
| |
| 24 |
|
| Calendaring & Scheduling |
| |
| | | | SHIL4WTMCR | This fix will prevent the Notes Client from crashing when opening a rescheduled meeting if the uninvited list is blank. | |
| | | | FSCT4P6SRK | Fixed a problem on Solaris and HP platforms where location and invitees were not sent to invitees on initial meeting invitations. | |
| | | | CFAR4WKRX4 | Fixed a problem with meeting cancellation working incorrectly for users added to a repeating meeting invitation after the original invitation was... | |
| | | | TIWI4X3KYU | Prevent corruption of repeating appointments which contain rich text fields, attachments, and/or doc links when they are edited by an iNotes... | |
| | | | DROS4BWLM6 | Fixed various problems with the corruption of rich text fields, attachments and doc links on calendar entries. | |
| | | | ASUH4ZVTF4 | Fix the incorrect layout of all-day events and anniversaries occurring on the same day when printing the daily calendar when Print first line only is... | |
| | | | APAI45PSQA | Resource reservation requests forwarded to resource owner indicate that the message has been sent from the server instead. With this fix, the notice... | |
| | | | EGN4YHGAB | Fixed memory leaks resulting from opening and closing or taking action upon certain types of calendar entries. | |
| | | | KHAN4XWLGG | This fix prevents an irrelevant repeat conflict warning received when rescheduling a single instance of an event. | |
| | | | PALT4UUV83 | Fixed a crash which occurred when rescheduling all instances of a repeating meeting, created in R4.x, that contained four or more doc... | |
| | | | SSHD4TSRH8 | Fix a client crash when creating meetings and doing resource lookups with cascading Address Books on the server. | |
| | | | MOA4CLL3Q | Prevent calendar documents from appearing in the All Documents view if the recipient's profile is set not to display them. | |
| | | | WCHI4ZZMYS | Fixed potential problems when working with very large repeating calendar entries (more than 250 instances). | |
| | | | DLIU4YW69U | The problem of receiving a failure when removing an invitee and adding or removing a room/resource at the same time has been fixed. | |
| | | | PZHN4Z7AEV | The Preference field, "Check for time conflicts," on calendar entries works. Users now receive an warning when two meetings are scheduled for the... | |
| | | | FZHG4ZE3LK | The problem that caused the server to crash when a delegate sent a meeting invitation using Calendar Author or Editor access is now... | |
| | | | DLIU4XFDA5 | Fixed a problem with resetting alarms. Prior to this fix the alarm was still on after turning it off. | |
| | | | DLIU4YG5RV | A decline notice is now sent to the chair if an invitee declines an invitation right after he proposes a counter invitation. | |
| | | | CFAR4ZALGK | The problem of creating an appointment and not setting an alarm, then editing the appointment and setting the alarm is now fixed. Previously, the... | |